Schema refactor#798
Merged
robholland merged 6 commits intov1from Dec 10, 2025
Merged
Conversation
This uses temporal-elasticsearch-tool where available, and a shell equivalent otherwise. Elasticsearch will now perform schema updates like Cassandra/SQL do. Simplify the broken setup vs upgrade toggles which did not properly control the behaviour. We don't have a way to with fixed toggles to separate creation from upgrade. Use a single toggle for management, the user can toggle that after install if they want to stop automatic upgrades.
michaely520
approved these changes
Dec 10, 2025
robholland
added a commit
that referenced
this pull request
Dec 18, 2025
* Remove prometheus dependency (#534) * Remove prometheus from dependencies and examples * Remove grafana dependency (#526) * Adjust some helper wiring. * Update Server Configmap (#794) * .ENV to env and add config template var * Simplify chart (#784) Simplify our helm chart, remove sub-charts. * Install cluster variations as part of CI. (#796) * Skip dockerize for 1.29.* images. This allows us to use server templated config files safely on 1.29.* and 1.30.* so that we can rollforward/backward without having to maintain two sets of configs. * Schema refactor (#798) * Refactor schema management. This uses temporal-elasticsearch-tool where available, and a shell equivalent otherwise. Elasticsearch will now perform schema updates like Cassandra/SQL do. Simplify the broken setup vs upgrade toggles which did not properly control the behaviour. We don't have a way to with fixed toggles to separate creation from upgrade. Use a single toggle for management, the user can toggle that after install if they want to stop automatic upgrades. * v1 doesn't have deps. (#800) * Push to the branch on which the action was triggered. * Update Chart to 1.0.0-rc.1. * Add some upgrading notes. (#805) * Fix version specifier. (#806) * Change image pull secrets to array instead of map (#701) * Correct config option name. (#807) * Pin helm unittest version due to helm 3 vs 4 compat issue. (#808) * Switch ct to testing against main. --------- Co-authored-by: Brian Kopp <briankopp.usa@gmail.com> Co-authored-by: PhilHenning <phillyp.henning@gmail.com> Co-authored-by: LeoDiazL <leo@bitovi.com> Co-authored-by: Phil Henning <philh@bitovi.com> Co-authored-by: Alex Stanfield <13949480+chaptersix@users.noreply.github.com> Co-authored-by: Temporal Data <commander-data@temporal.io> Co-authored-by: Matthew Brandman <matthb6@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was changed
Adjusted the schema management to work per store. Use temporal-elasticsearch-tool when available.
Why?
This allows people to opt-in to schema management per store rather than on/off globally. The configuration also now better matches our behaviour. For example previously if
setupwas enabled it would accidentally also perform upgrades even ifupgradewas disabled. Now we have just one toggle that controls whether we manage the schema. Users can disable that after initial install to prevent future upgrades.Elasticsearch now supports upgrades like Cassandra/SQL do. Using temporal-elasticsearch-tool (on supported images after 1.30 release) will allow use of AWS authentication for Elasticsearch which the current
curlbased automation did not.